Social networking with video annotation

ABSTRACT

A method and system for annotating Playable Media Files in a social network having a plurality of members, wherein the method includes receiving the Playable Media File from a first member, receiving an annotation from another member, and saving the annotation in a file other than the Playable Media File.

CROSS-REFERENCE TO RELATED APPLICATIONS

This is a Continuation-In-Part Patent Application of a U.S. Non-Provisional Patent Application having Ser. No. 14/170,149, filed on Jan. 31, 2104, now U.S. Pat. No. 9,451,001, which claimed priority to U.S. Provisional Patent Application having Ser. No. 61/759,219, filed on Jan. 31, 2013. The disclosure of each of the above-identified patent documents is incorporated herein by reference in its entirety.

FIELD OF THE INVENTION

Embodiments generally relate to assemblies, methods, devices, and systems for managing information, and more particularly, to assemblies, methods, devices, and systems for sharing and annotating video data between members of a social network.

SUMMARY OF THE INVENTION

A method to create and save an annotation associated with a Playable Media File is disclosed. The method includes receiving a Playable Media File, creating an annotation relating to the Playable Media File, providing the annotation to a network server, providing a data profile to the network server, wherein the data profile comprises a location in the Playable Media File where the annotation should be made visible, determining by the network server if the annotation is a first annotation submitted for the Playable media File, if the annotation is not a first annotation submitted for the Playable Media File, encoding the data profile in a previously-created table of contents for the Playable Media File, if the annotation is a first annotation submitted for the Playable Media File, then creating a table of contents by the network server for the Playable Media File and encoding by the network server the data profile in the table of contents, wherein the Playable Media File is selected from the group consisting of an audio file, a video file, an audiovisual file, slide show, AVI file, MP3 file, MP4 file, WMA file, WAV file, Flash, and MPEG file.

An article of manufacture is disclosed. Applicants' article of manufacture comprises a processor, a computer readable medium comprising computer readable program code disposed therein to create and save an annotation associated with a Playable Media File, the computer readable program code comprising a series of computer readable program steps to cause the processor to effect receiving a Playable Media File, creating an annotation relating to the Playable Media File, providing the annotation to a network server, providing a data profile to the network server, wherein the data profile comprises a location in the Playable Media File where the annotation should be made visible, determining by the network server if the annotation is a first annotation submitted for the Playable media File, if the annotation is not a first annotation submitted for the Playable Media File, encoding the data profile in a previously-created table of contents for the Playable Media File, if the annotation is a first annotation submitted for the Playable Media File, then creating a table of contents by the network server for the Playable Media File and encoding by the network server the data profile in the table of contents, wherein the Playable Media File is selected from the group consisting of an audio file, a video file, an audiovisual file, slide show, AVI file, MP3 file, MP4 file, WMA file, WAV file, Flash, and MPEG file.

A non-transitory computer usable medium encoded with a computer program product to create and save an annotation associated with a Playable Media File and usable with programmable computer processor disposed within a controller, is disclosed. Applicants' computer program product comprises computer readable program code which causes the programmable computer processor to receive a Playable Media File, create an annotation relating to the Playable Media File, provide the annotation to a network server, provide a data profile to the network server, wherein the data profile comprises a location in the Playable Media File where the annotation should be made visible, determine by the network server if the annotation is a first annotation submitted for the Playable media File, if the annotation is not a first annotation submitted for the Playable Media File, encode the data profile in a previously-created table of contents for the Playable Media File, if the annotation is a first annotation submitted for the Playable Media File, then create a table of contents by the network server for the Playable Media File and encode by the network server the data profile in the table of contents, wherein the Playable Media File is selected from the group consisting of an audio file, a video file, an audiovisual file, slide show, AVI file, MP3 file, MP4 file, WMA file, WAV file, Flash, and MPEG file.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention will be better understood from a reading of the following detailed description taken in conjunction with the drawings in which like reference designators are used to designate like elements, and in which:

FIG. 1 illustrates an exemplary embodiment of a system for annotating video within a social network;

FIG. 2 illustrates another exemplary embodiment of a system for annotating video within a social network;

FIG. 3 is a table of information fields stored in association with each Playable Media File;

FIG. 4 is a flowchart of the method and/or process related to annotating Playable Media File within a social network;

FIG. 5A summarizes additional steps in Applicants' method, additional steps implemented by Applicants' article of manufacture, and additional steps performed by a programmable processor implementing Applicants' computer program product;

FIG. 5B summarizes additional steps in Applicants' method, additional steps implemented by Applicants' article of manufacture, and additional steps performed by a programmable processor implementing Applicants' computer program product;

FIG. 6 summarizes additional steps in Applicants' method, additional steps implemented by Applicants' article of manufacture, and additional steps performed by a programmable processor implementing Applicants' computer program product;

FIG. 7 summarizes additional steps in Applicants' method, additional steps implemented by Applicants' article of manufacture, and additional steps performed by a programmable processor implementing Applicants' computer program product;

FIG. 8 summarizes additional steps in Applicants' method, additional steps implemented by Applicants' article of manufacture, and additional steps performed by a programmable processor implementing Applicants' computer program product;

FIG. 9 summarizes additional steps in Applicants' method, additional steps implemented by Applicants' article of manufacture, and additional steps performed by a programmable processor implementing Applicants' computer program product;

FIG. 10 summarizes additional steps in Applicants' method, additional steps implemented by Applicants' article of manufacture, and additional steps performed by a programmable processor implementing Applicants' computer program product;

FIG. 11 summarizes additional steps in Applicants' method, additional steps implemented by Applicants' article of manufacture, and additional steps performed by a programmable processor implementing Applicants' computer program product;

FIG. 12 summarizes additional steps in Applicants' method, additional steps implemented by Applicants' article of manufacture, and additional steps performed by a programmable processor implementing Applicants' computer program product; and

FIG. 13 summarizes additional steps in Applicants' method, additional steps implemented by Applicants' article of manufacture, and additional steps performed by a programmable processor implementing Applicants' computer program product.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The invention is described in preferred embodiments in the following description with reference to the FIGs., in which like numbers represent the same or similar elements. Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” “in certain embodiments,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment. It is noted that, as used in this description, the singular forms “a,” “an” and “the” include plural referents unless the context clearly dictates otherwise.

The described features, structures, or characteristics of the invention(s) may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are recited to provide a thorough understanding of embodiments of the invention(s). One skilled in the relevant art will recognize, however, that the invention(s) may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the invention.

The schematic flow chart diagrams included are generally set forth as a logical flowchart diagram (e.g., FIGS. 4, 5A, 5B, 6, 7, 8, 9, 10, 11, 12, and 13). As such, the depicted order and labeled steps are indicative of one embodiment of the presented method. In certain embodiments, other steps and methods are conceived that are equivalent in function, logic, or effect to one or more steps, or portions thereof, of the illustrated method. Additionally, the format and symbols employed are provided to explain the logical steps of the method and are understood not to limit the scope of the method. Although various arrow types and line types are employed in the flowchart diagrams, they are understood not to limit the scope of the corresponding method (e.g., FIGS. 4, 5A, 5B, 6, 7, 8, 9, 10, 11, 12, and 13). Indeed, some arrows or other connectors may be used to indicate only the logical flow of the method. For instance, an arrow indicates a waiting or monitoring period of unspecified duration between enumerated steps of the depicted method. Additionally, the order in which a particular method occurs may or may not strictly adhere to the order of the corresponding steps shown.

In certain embodiments, individual steps recited in FIGS. 4, 5A, 5B, 6, 7, 8, 9, 10, 11, 12, and 13, are combined, eliminated, or reordered.

Applicants' system and method includes a network wherein a video can be created using any available video format, and that video can be shared between a plurality of people. In certain embodiments, Applicants' system and method can be used by multiple members of a social network to associate annotations with a Playable Media File, and/or to initiate discussion threads associated with that Playable Media File.

Referring to FIG. 1, a portion of Applicants' network 100 is illustrated. In certain embodiments, Applicants' network 100 comprises a social network. In certain embodiments, Applicants' social network 100 is an open social network. In certain embodiments, Applicants' social network 100 is a closed social network.

In the illustrated embodiment of FIG. 1, network 100 comprises a network server 130 that is communicatively connected to a computing device 110 through a first communication fabric 120 and a computing device 150 through a second communication fabric 140. In certain embodiments, the network server 130 is owned and/or operated by a social networking service provider while computing devices 110 and 150 are owned and/or operated by users or members of the social network 100, where a member has a profile containing information about the member stored in information 137 of the social network server 130. In some embodiments, the computing device 110 is owned and operated by a first member and the computing device 150 is owned and operated by a second member.

For the sake of clarity, FIG. 1 shows a first computing device 110, network server 130, and a second computing device 150. FIG. 1 should not be taken as limiting. Rather, in other embodiments any number of entities and corresponding devices can be part of the network 100, and further, although FIG. 1 shows two communication fabrics 120 and 140, in other embodiments, less then, or more than, two communication fabrics are provided in the social network 100. For example, in certain embodiments, the communication fabric 120 and the communication fabric 140 are the same communication fabric.

In certain embodiments, the computing devices 110 and 150 and host 130 are each an article of manufacture. Examples of the article of manufacture include: a server, a mainframe computer, a mobile telephone, a smart telephone, a personal digital assistant, a personal computer, a laptop, a set-top box, an MP3 player, an email enabled device, a tablet computer, a web enabled device, or other special purpose computer each having one or more processors (e.g., a Central Processing Unit, a Graphical Processing Unit, or a microprocessor) that are configured to execute Applicants' API to receive information fields, transmit information fields, store information fields, or perform methods.

By way of illustration and not limitation, FIG. 1 illustrates the computing device 110, the network server 130, and the computing device 150 as each including a processor 112, 132, and 152, respectively, a non-transitory computer readable medium 113, 133, and 153, respectively, having a series of instructions 114, 134, and 154, respectively, encoded therein, an input/output means 111, 131, and 151, respectively, such as a keyboard, a mouse, a stylus, touch screen, a camera, a scanner, or a printer. Computer readable program code 114, 134, and 154 is encoded in non-transitory computer readable media 113, 133, and 153, respectively. Processors 112, 132, and 152 utilize computer readable program code 114, 134, and 154, respectively, to operate computing devices 110, 130, and 150, respectively. In certain embodiments, the computing device 110, 130, and 150 employ hardware and/or software that supports accelerometers, gyroscopes, magnetometers (e.g., solid state compasses) and the like.

Processors 112 and 152 utilize Applicants' Application Program Interfaces (APIs) 116 and 156, respectively, encoded in computer readable media 113 and 153, respectively, to communicate with host 130 and access Applicants' algorithm 136 encoded in computer readable medium 133 to implement Applicants' social network and method described herein. Algorithm 136 comprises Applicants' source code to operate a public or private social network, and when implemented by computing device 110 causes a graphic user interface (“GUI”) to be displayed on display screen 115, wherein that GUI comprises and displays a plurality of graphical interactable objects. A member using computing device 110 (or computing device 150) can utilize that GUI to access a logical volume, such as for example and without limitation logical volume 180 (FIG. 2), wherein information specific to that user are encoded in logical volume 180. The member and/or user can further utilize the GUI to access Applicants' social network as described herein.

Processor 132 accesses the computer readable program code 134, encoded on the non-transitory computer readable medium 133, and executes an instruction 136 to electronically communicate with the computing device 110 via the communication fabric 120 or electronically communicate with the computing device 150 via the communication fabric 140. Encoded information 137 includes, for example and without limitation, the data communicated or information fields communicated, e.g., date and time of transmission, frequency of transmission and the like, with any or all of the computing device 110 and the computing device 150. In certain embodiments, information 137 is analyzed and/or mined. In certain embodiments, information 137 is encoded in a plurality of individual logical volumes specific to each member/user.

In certain embodiments, computing devices 110 and 150 further comprise one or more display screens 115 and 155, respectively. In certain embodiments, display screens 115 and 155 comprise an LED display device.

In certain embodiments, the information fields received from the computing device 110 at the network server 130 are exchanged with other computing devices not shown in FIG. 1. For example, information fields received from a social network in which the member has an Internet presence is sent to the social network server 130 and stored at the information 137 in association with a profile of the member. Alternatively, or in combination, the information fields transmitted from the computing device 110 to the social network server 130 is sent to an account of the member within the social network.

In certain embodiments, information 137 is encoded in one or more hard disk drives, tape cartridge libraries, optical disks, combinations thereof, and/or any suitable data storage medium, storing one or more databases, or the components thereof, in a single location or in multiple locations, or as an array such as a Direct Access Storage Device (DASD), redundant array of independent disks (RAID), virtualization device, etc. In certain embodiments, information 137 is structured by a database model, such as a relational model, a hierarchical model, a network model, an entity-relationship model, an object-oriented model, or a combination thereof. For example, in certain embodiments, the information 137 is structured in a relational model that stores a plurality of Identities for each of a plurality of members as attributes in a matrix.

In certain embodiments, the computing devices 110, 130, and 150 include wired and/or wireless communication devices which employ various communication protocols including near field (e.g., “Blue Tooth”) and/or far field communication capabilities (e.g., satellite communication or communication to cell sites of a cellular network) that support any number of services such as: telephony, Short Message Service (SMS) for text messaging, Multimedia Messaging Service (MMS) for transfer of photographs and videos, electronic mail (email) access, or Global Positioning System (GPS) service, for example.

As illustrated in FIG. 1, the communication fabrics 120 and 140 each comprise one or more switches 121 and 141, respectively. In certain embodiments, communication fabrics 120 and 140 are the same. In certain embodiments, at least one of the communication fabrics 120 and 140 comprises the Internet, an intranet, an extranet, a storage area network (SAN), a wide area network (WAN), a local area network (LAN), a virtual private network, a satellite communications network, an interactive television network, or any combination of the foregoing. In certain embodiments, at least one of the communication fabrics 120 and 140 contains either or both wired or wireless connections for the transmission of signals including electrical connections, magnetic connections, or a combination thereof. Examples of these types of connections include: radio frequency connections, optical connections, telephone links, a Digital Subscriber Line, or a cable link. Moreover, communication fabrics 120 and 140 utilize any of a variety of communication protocols, such as Transmission Control Protocol/Internet Protocol (TCP/IP), for example.

Referring to FIG. 2, the computing devices 110, 130 and 150 are each communicatively connected to the communication fabric 120, such as a WAN or Internet. The network server 130 is a computing device that is owned and/or operated by a networking service provider, and computing devices 110 and 150 are owned and/or operated by individual network users. In certain embodiments, network server is owned and/or operated by a social network provider. In certain embodiments, the network server 130 provides access to the computing devices 110 and 150 to execute Applicants' source code 136 via a Software as a Service (SaaS) means.

In certain embodiments information fields are received from one or more computing devices 110, 130 and/or 150 and stored on the “Cloud” such as data storage library 160 and/or 170. Referring to FIG. 2, each of the data storage libraries 160 and 170 have corresponding physical storage devices, such as and without limitation physical data storage devices 163-169 for data storage library 160 and 173-179 for data storage library 170.

In certain embodiments, data storage library 160 and data storage library 170 are configured in a Peer To Peer Remote Copy (“PPRC”) storage system, wherein the information fields in data storage library 160 is automatically backed up in data storage library 170. In certain embodiments, Applicants' PPRC storage system utilizes synchronous copying. In certain embodiments, Applicants' PPRC storage system utilizes asynchronous copying.

In the illustrated embodiment of FIG. 2, physical storage device 163 is configured to comprise logical volume 180. In certain embodiments, each physical storage device in data storage library 160 is configured to comprise a plurality of logical volumes. Similarly, each physical storage device in data storage library 170 is configured to comprise a corresponding plurality of logical volumes. In certain embodiments, each member of the social network is assigned a unique logical volume. In such embodiments a permission file 157 may be encoded in computer readable medium 133 or in data storage libraries 160 and 170 that associates each logical volume with a social network member and further associates each logical volume with access permissions for certain designated other social network users. Each social network user configures his/her own logical volume permissions. In certain embodiments, if a first user desires to remove access permissions from a second user, that first member simply accesses his/her permissions file and deletes the second user. Thereafter, the second user cannot retrieve data stored on the logical volume associated with the first user.

Referring to FIGS. 1, 2, and 3, Applicants algorithm 136, and its functions, can be accessed by users of Applicants' network 100 to create, share, edit, associate one or more annotations with, and/or associate one or more discussion threads with, a Playable Media File. One member, using a computing device such as computing device 110 or 150, to access network server 130, streams a Playable Media File from its original storage location. In certain embodiments the Playable Media File is encoded in a unique logical volume accessible by a first user. That first user can grant access to the Playable Media File to one or more other users by storing access permissions in permission file 157. In certain embodiments the access includes levels such as, and without limitation, view only, view/edit, view/edit/share, and the like. In certain embodiments the access includes conditions or restrictions such as expirations dates, limitations on the number of times the file can be viewed, and the like.

Referring now to 3, when a user having permission streams the Playable Media file, and if that user associates an annotation with the Playable Media File, a data profile 300 is created for the Playable Media File and is stored on network server 130, and optionally on data storage library 160 or 170. Data profile 300 includes various information fields, including the Global Unique Identifier (GUID) 302 associated with the creating member, a description 304 of the Playable Media File (e.g., a title), and permissions 306 held by various members to access, edit, and/or share the Playable Media File. Data profile 300 may further include subsequently added annotations 312 and discussion threads 328.

Applicants algorithm 136 provides the ability for each user having access to the Playable Media File to associate annotations for display at various timeline locations as the Playable Media File is streamed from its original storage location. Such annotations may be any known format and may include text, video, audio, pictures, or a combination thereof, and are stored as a separate file. When subsequent viewers execute the Playable Media File the annotation(s) will be visible at the specified time segment. In certain such embodiments, the annotation is shown in the same window as the Playable Media File and may be visible over the Playable Media File. In other embodiments, the annotation is shown in a separate window. Applicants' algorithm 136 generates a timeline which displays when the Playable Media File is streamed.

In certain embodiments, the member creating the annotation can set permissions for the annotation, restricting who can view or edit the annotation. In such embodiments, the permissions are stored in permission file 157. Referring now to FIG. 4, in step 410 a first network user encodes a first Playable Media file in a first storage location. In step 420, the first user receives a request to share the first Playable Media File with a second network user. In step 430, the first network user grants access to the first Playable Media File to the requesting second network user. The first user's grant of access right to the second network user is encoded in a permission file 157. In step 440, the network server provides notice to the second network user regarding that second user's access privilege(s) to access the first Playable Media File from the first storage location. In certain embodiments the notice may further include a link to the Playable Media File or information about where and how to access the Playable Media File.

For those Playable Media Files having annotations, data profile 300 further contains information fields concerning each annotation 312(a)-(n), including one or more of the type 320 of the annotation (text, audio, video, picture, etc.), the location 322 of the associated annotation within the Playable Media File, the GUID 324 of the member who initiated the annotation, and a description 326 for the annotation, such as a title or other descriptor.

In certain embodiments Applicants' algorithm 136 further generates a table of contents of the annotations added to the Playable Media File using the information in data profile 300, including a link to each annotation. The link may be in the form of a pointer, electronic bookmark, hyperlink, or any other type of link. Where the link is a hyperlink, the hyperlink may link to an annotation that is saved as a different file on data storage library 160 or 170. In certain embodiments, annotation(s) may be viewed and edited separately from the Playable Media File. For each new annotation added to the Playable Media File, Applicants' algorithm 136 updates the table of contents. In such embodiments, the table of contents may include one or more of a caption or other description of the annotation, the time of the annotation within the Playable Media File, the author of the annotation, and the date and/or time the annotation was made.

FIG. 5 summarizes Applicants' method to save and share annotations associated with a Playable Media File. Referring now to FIG. 5, in step 510 the method encodes an annotation to be associated with a Playable Media File in a storage location, i.e. a file, that differs from the Playable Media File. In certain embodiments, step 510 is performed by Applicants' algorithm 136. In certain embodiments, step 510 is performed by the user creating the annotation.

In certain embodiments, the “visibility” for annotation saved in step 510 is by default defined as “public,” meaning that any other user who has permission to stream the Playable Media File has permission to stream that “public” annotation. In step 520, Applicants' method determines whether to change that “visibility” from “public” to “private.”

If the method elects in step 520 not to change the visibility from public to private, then the method transitions from step 520 to step 530 and includes a storage location for the saved annotation in a sitemap published to search engines. Applicants' method transitions from step 530 to step 570.

Alternatively, if the method elects in step 520 to change the visibility from public to private, then the method transitions from step 520 to step 540 and does not include a storage location for the saved annotation in a sitemap published to search engines. In certain embodiments, step 540 is performed by Applicants' network server 130. In certain embodiments, step 540 is performed by Applicants' algorithm 136.

Applicants' method transitions from step 540 to step 550 wherein the method determines whether to share the saved annotation to specific recipients. In certain embodiments, step 550 is performed by Applicants' network server 130. In certain embodiments, step 550 is performed by Applicants' algorithm 136.

If Applicants' method elects in step 550 to not share the annotation with specific recipients, then the method transitions from step 550 to step 570. Alternatively, if Applicants' method elects in step 550 to share the annotation with specific recipients, then the method transitions from step 550 to step 560 wherein the user to prompted to enters recipients in the form of name(s), and/or email address, and/or social media account. Applicants' method transitions from step 560 to step 570.

In step 570, the method determines if the annotation encoded in step 510 is the first annotation for the Playable Media File. If the method determines if the annotation saved in step 510 comprises a first annotation for the Playable Media File, then the method transitions to step 590 wherein a table of contents is created for the Playable Media File. Alternatively, if the annotation is not the first and the Playable Media File already has a table of contents, then the method transitions to step 580 wherein the method updates the table of contents to include an entry for the saved annotation of step 510. For example, upon receipt of an annotation from computing device 150 of the second user, network server 130 determines if the Playable Media File already has annotations (and thus a table of contents) by checking annotations field 312 (FIG. 3) of data profile 300. If no annotations are included in the Playable Media File, the network server 130 creates a table of contents using the data in data profile 300 and the annotation and any related information received from computing device 150. In certain embodiments the table of contents is then saved separately from the Playable Media File. In certain embodiments, the table of contents is stored on Applicants' network server 130. In certain such embodiments, the table of contents is associated with the Playable Media File such that it is always presented to a user viewing the Playable Media File. In other embodiments, the table of contents may be viewed separately from the Playable Media File.

Referring now to FIG. 5B, in certain embodiments, Applicants' method can initiate a discussion thread to be displayed at a specific timeline location of the Playable Media File. In step 505, Applicants' network server receives a request from a member to initiate a discussion thread at a specified timeline location in the Playable Media File. In step 515, Applicants' algorithm 136 generates the discussion thread to become visible when the Playable Media File is streamed and viewed at the timeline specified. In certain embodiments the request further includes a type identifier indicating whether the discussion thread is to be open or closed. Where the open identifier is provided, the discussion thread is open to all members and therefore any member may view and add a comment to the discussion thread. Where the closed identifier is provided, the discussion thread is private and only available to particular members. In such embodiments the request provided by the initiating member includes identifiers for one or more members that are to have access to the discussion thread. In certain such embodiments Applicants' algorithm 136 further sends invitations to the identified members to invite them to participate in the thread. In certain such embodiments, the permissions given to various members to access and participate in the discussion thread is stored in permissions file 157.

Members having access to the Playable Media File can then add written, audible, pictorial, or video comments to the thread. In step 525, Applicants network server receives content for inclusion in the discussion thread. In step 535, Applicants' method adds a descriptor and a timeline for the discussion thread in a Table of Contents associated with the Playable Media File. In step 545, additional content for the discussion thread that is later received is added to the discussion thread in the order received. Further in step 545, a descriptor for that later-added content is added to the Table of Contents.

In certain embodiments only members having edit privileges can post in the discussion thread. In certain embodiments only individuals having specific discussion thread privileges can post in the discussion thread. In certain embodiments, the privilege to post in a thread is specific to the particular thread, and therefore a member may have access to post in one thread but not another. In certain embodiments, the discussion thread is visible to any individual viewing the Playable Media File. In other embodiments, the discussion thread is visible only to certain individuals, such as those that have been given specific access to the thread or those that have edit privileges for the video.

For Playable Media Files having discussion threads, data profile 300 further includes information fields for each discussion thread 328, including for each comment 330(a)-(n) made in the discussion thread by a member, the GUID of the member author of the comment, and a description 334, which may be the comment itself or another identifier.

Applicants' further disclose an article of manufacture comprising a platform for information management, such as computing device 110, 130, and/or 150, comprising computer readable program code, such as API 116, API 156, and/or Applicants' social network source code 136, residing in anon-transitory computer readable medium, such as computer readable medium 113, 133, and/or 153, where that computer readable program code can be executed by a processor, such as processor 112 (FIG. 1) and/or 132 (FIG. 1), and/or 152, to implement Applicants' method recited in FIGS. 4, 5A, 5B, 6, 7, 8, 9, 10, and 11.

Applicants further disclose a non-transitory computer readable medium wherein Applicants' computer program product is encoded herein. Applicants' computer program product comprises computer readable program code that can be executed by a programmable processor to implement Applicants' method recited in FIGS. 4, 5A, 5B, 6, 7, 8, 9, 10, and 11. In either case, in certain embodiments, the computer readable program code is encoded in a non-transitory computer readable medium comprising, for example, a magnetic information storage medium, an optical information storage medium, an electronic information storage medium, and the like. “Electronic storage media,” means, for example and without limitation, one or more devices, such as and without limitation, a PROM, EPROM, EEPROM, Flash PROM, compactflash, smartmedia, and the like.

Referring now to FIG. 6, in step 610 Applicants disclose determining whether to create a plurality of virtual clips, wherein each virtual clip comprises content encoded in one or more Media File, playable or static, from a beginning of the Media File, playable or static, up to a designated end point, wherein “Media File, playable or static,” means a file selected from the group consisting of an audio file, a video file, an audiovisual file, slide show file, AVI file, MP3 file, MP4 file, WMA file, WAV file, Flash, MPEG file, an image file (JPG, TIF, PNG, GIF, Bitmap, and the like), a PDF file, a text file, a VISIO file, a .ppt file, a .key file, a spreadsheet file, and any type of 3D media file. In certain embodiments, such a 3D media file requires holographic projection/holographic viewing. In certain embodiments, “Media File, playable or static,” further includes any file which generates a Stereoscopic visual display that can be viewed through stereoscopic eyewear or played on 3D display technology such as 3D TV, and in certain embodiments comprises a Virtual Reality/Augmented Realty file that can be viewed through Virtual Reality devices such as Hololense, Oculus Rift, Sony Playstation VR, HCT VIVE, Razer OSBR HDK, Zeiss VR1, SOV VR, Freefly, and the like.

If a user elects to create such a plurality of virtual clips, the method transitions from step 610 to step 710 (FIG. 7). Referring now to FIG. 7, in step 710 the method, without pausing the media play, displays an END CLIP interactable graphical object and a CANCEL CLIP interactable graphical object.

If the user activates the CANCEL CLIP interactable graphical object in step 720, then the method transitions from step 720 to step 750 and ends. Alternatively, if the user does not activate the CANCEL CLIP interactable graphical object in step 710, then the method transitions from step 710 to step 730 wherein the method determines if the END CLIP interactable graphical object has been activated. If the method determines in step 730 that the END CLIP interactable graphical object has not been activated, then the method pauses at step 730 until the user activates the END CLIP interactable graphical object, wherein the method transitions from step 730 to step 740 wherein the method temporarily stores a begin time, end time, and total media duration.

In certain embodiments, in step 740 an end timeline location, and the total media duration are saved to the user's computing device. In certain embodiments, in step 740 the begin time, the end time, and a total media duration are saved to Applicants' network server 130 (FIG. 1).

If the user elects in step 610 NOT to create a plurality of virtual clips each from a beginning to a designated end point, then the method transitions from step 610 to step 620 wherein the method may elect to create a plurality of virtual clips comprising content from one or more Media File, playable or static from a designated start point to a designated end point. If the user elects to create a plurality of virtual clips, where each virtual clip comprises content from one or more Media File, playable or statics, and wherein the user specifies a designated timeline location to begin the virtual clip, then the method transitions from step 620 to step 810 (FIG. 8).

Referring now to FIG. 8, in step 810 the method streams the Media File, playable or static from a designated start point, and without pausing the media play, displays an END CLIP interactable graphical object and a CANCEL CLIP interactable graphical object.

If the user activates the CANCEL CLIP interactable graphical object in step 820, then the method transitions from step 820 to step 850 and ends. Alternatively, if the user does not activate the CANCEL CLIP interactable graphical object in step 810, then the method transitions from step 810 to step 830 wherein the method determines if the END CLIP interactable graphical object has been activated. If the method determines in step 830 that the END CLIP interactable graphical object has not been activated, then the method pauses at step 830 until the user activates the END CLIP interactable graphical object, wherein the method transitions from step 830 to step 840 wherein the method temporarily stores a begin time, end time, and total media duration.

In certain embodiments, in step 740 a begin timeline location, an end timeline location, and the total media duration are saved to the user's computing device. In certain embodiments, in step 740 the begin time, the end time, and a total media duration are saved to Applicants' network server 130 (FIG. 1).

If the user elects in step 610 NOT to create a plurality of virtual clips each from a beginning to a designated end point, and if the user elects NOT to create a plurality of virtual clips, where each virtual clip comprises content from one or more Media File, playable or statics, and wherein the user specifies a designated timeline location to begin the virtual clip, then the method transitions from step 620 to step 630 wherein the method determines if the user elects to configure a composite virtual clip.

If the user elects to configure a composite virtual clip in step 630, the method transitions from step 630 to step 910. Referring now to FIG. 9, in step 910 the method selects (N) saved virtual clips to configure a composite virtual clip, and determines an order of presentation for those (N) virtual clips.

In step 920, the method sets (M) initially to 1. In step 930, the method configures a (M)th link to a (M)th saved virtual clip, wherein the (M)th saved virtual clip will be the (M)th virtual clip to be displayed when the composite virtual clip is activated. In step 930, the method saves the (M)th link in a composite virtual clip file.

In step 950, the method determines if (M) equals (N), i.e. if all (N) links to the (N) selected (N) saved virtual clips have been created and saved. If the method determines in step 950 that (M) does not equal (N), then the method transitions from step 950 to step 960 wherein the method increments (M) by 1, i.e. sets (M) equal to (M)+1. The method transitions from step 960 to step 930 and continues as described herein. Alternatively, if the method determines in step 950 that (M) equals (N), then the method transitions from step 950 to step 970 and ends.

If the user elects in step 610 NOT to create a plurality of virtual clips each from a beginning to a designated end point, and if the user elects in step 620 NOT to create a plurality of virtual clips, where each virtual clip comprises content from one or more Media File, playable or statics, and wherein the user specifies a designated timeline location to begin the virtual clip, and if the user does NOT elect in step 630 to configure a composite virtual clip in step 630, then in step 640 the method determines whether to display a composite virtual clip.

If the user elects to display a composite virtual clip in step 640, the method transitions to step 1010 where the method provides a storage location for a composite virtual clip file configured to access (M) saved clips. In step 1020, the method sets (P) initially to 1. In step 1030 the method activates a (P)th link encoded in the composite virtual clip file to stream a (P)th saved virtual clip to the users device.

In step 1040 the method determines if all (N) clips comprising the selected composite virtual clip have been displayed, i.e. if (P) equals (N). If the method determines in step 1040 that (p) does not equal (N), then the method transitions from step 1040 to step 1050 and increments (P) by 1, i.e. sets (P) equal to (P)+1. The method transitions from step 1050 to step 1030 and continues as described herein. Alternatively, if the method determines in step 1040 that (P) equals (N), the method transitions to step 1060 and ends.

If a user elects in step 650 to apply one or more transitioning effect to one or more saved virtual clips, then the method transitions from step 650 to step 1110. As those skilled in the art will appreciate, a “transition” comprises an animation-like effect when Applicants' method to display a composite virtual clip moves from one previously saved virtual clip to a next previously saved virtual clip during an on-screen presentation. Applicants' method allows control the speed of each transition effect. In addition, Applicants' method also permits the addition of sound transitions when moving from a saved virtual clip to the next saved virtual clip.

If a user desires in step 650 to add one or more transition effects to a previously configured composite virtual clip, Applicants' method transitions from step 650 to step 1110 (FIG. 11). Referring now to FIG. 11, in step 1110 the method selects a previously configured composite virtual clip, wherein that composite virtual clip is configured to include (N) previously saved virtual clips in an order from 1 to (N).

In step 1120, the method selects a transition effect having a known storage location. In step 1130, the method configures an (i)th transition effect link pointing to the known storage location for the desired transition effect.

In step 1140, the method configures the (i)th transition effect link to be activated after activation of a link to an (i)th virtual clip and before activation of a link to an (i+1)th virtual clip. In step 1150, the method updates the composite virtual clip file to include the (i)th transition effect link.

In step 1160, the method determines if the user desires to configure additional transition effects for the selected composite virtual clip. If the user elects to configure additional transition effect links, then the method transition from step 1160 to step 1120 and continues as described herein. Alternatively, if the user does not elect to configure additional transition effect links, then the method transition from step 1160 to step 1170 and ends.

If a user desires in step 660 to add one or more lensing effects to a previously configured composite virtual clip, Applicants' method transitions from step 660 to step 1210 (FIG. 12) As those skilled in the art will appreciate, a “lensing” effect includes, for example and without limitation, overlay of one or more color filters, image distortions, and annotations.

Referring now to FIG. 12, in step 1210 the method selects a previously configured composite virtual clip, wherein that composite virtual clip is configured to include (N) previously saved virtual clips in an order from 1 to (N).

In step 1220, the method selects a lensing effect having a known storage location. In step 1230, the method configures an (i)th lensing effect link pointing to the known storage location for the desired lensing effect.

In step 1240, the method configures the (i)th lensing effect link to be simultaneously with activation of a link to an (i)th virtual clip. In step 1250, the method updates the composite virtual clip file to include the (i)th lensing effect link.

In step 1260, the method determines if the user desires to configure additional lensing effects for the selected composite virtual clip. If the user elects to configure additional transition effect links, then the method transition from step 1260 to step 1220 and continues as described herein. Alternatively, if the user does not elect to configure additional transition effect links, then the method transition from step 1260 to step 1270 and ends.

If a user desires in step 670 to add one or more sound effects to a previously configured composite virtual clip, Applicants method transitions from step 670 to step 1310 (FIG. 13). Referring now to FIG. 13, in step 1310 the method selects a previously configured composite virtual clip, wherein that composite virtual clip is configured to include (N) previously saved virtual clips in an order from 1 to (N).

In step 1320, the method selects a sound effect having a known storage location. In step 1330, the method configures an (i)th sound effect link pointing to the known storage location for the desired lensing effect.

In step 1340, the method configures the (i)th sound effect link to be simultaneously with activation of a link to an (i)th virtual clip. In step 1350, the method updates the composite virtual clip file to include the (i)th sound effect link.

In step 1360, the method determines if the user desires to configure additional sound effects for the selected composite virtual clip. If the user elects to configure additional sound effect links, then the method transition from step 1360 to step 1320 and continues as described herein. Alternatively, if the user does not elect to configure additional sound effect links, then the method transition from step 1360 to step 1370 and ends.

While the preferred embodiments of the present invention have been illustrated in detail, it should be apparent that modifications and adaptations to those embodiments may occur to one skilled in the art without departing from the scope of the present invention as set forth herein. 

We claim:
 1. A method to create and save an annotation associated with a Playable Media File, comprising: receiving a Playable Media File; creating an annotation relating to said Playable Media File; providing said annotation to a network server; providing a data profile to said network server, wherein said data profile comprises a location in said Playable Media File where said annotation should be made visible; determining by said network server if said annotation is a first annotation submitted for said Playable media File; if said annotation is not a first annotation submitted for said Playable Media File, encoding said data profile in a previously-created table of contents for said Playable Media File; if said annotation is a first annotation submitted for said Playable Media File: creating a table of contents by said network server for said Playable Media File; and encoding by said network server said data profile in said table of contents; wherein said Playable Media File is selected from the group consisting of an audio file, a video file, an audiovisual file, slide show, AVI file, MP3 file, MP4 file, WMA file, WAV file, Flash, and MPEG file.
 2. The method of claim 1, further comprising initiating a discussion thread within said Playable Media File at said location.
 3. The method of claim 1, wherein: said receiving further comprises receiving a Playable Media file by a first member of a social network; said creating further comprises creating an annotation by said first member of said social network; and said providing steps are performed by said first member of said social network.
 4. The method of claim 3, wherein said initiating further comprises initiating by said first member a discussion thread within said Playable Media File at said location.
 5. The method of claim 1, further comprising storing said annotation as a file separate from said Playable Media File.
 6. The method of claim 5, further comprising executing said Playable Media File by a second member of said social network.
 7. The method of claim 6, wherein said first member differs from said second member.
 8. The method of claim 6, wherein said first member and said second member are the same.
 9. The method of claim 6, further comprising when said Playable Media File reaches said location, making said annotation visible.
 10. The method of claim 9, further comprising: displaying said executing Playable Media File in a first window; and displaying said annotation in a second window.
 11. The method of claim 9, further comprising displaying both said executing Playable Media File and said annotation in the same window.
 12. An article of manufacture comprising a processor, a computer readable medium comprising computer readable program code disposed therein to create and save an annotation associated with a Playable Media File, the computer readable program code comprising a series of computer readable program steps to cause the processor to effect: receiving a Playable Media File; creating an annotation relating to said Playable Media File; providing said annotation to a network server; providing a data profile to said network server, wherein said data profile comprises a location in said Playable Media File where said annotation should be made visible; determining by said network server if said annotation is a first annotation submitted for said Playable media File; if said annotation is not a first annotation submitted for said Playable Media File, encoding said data profile in a previously-created table of contents for said Playable Media File; if said annotation is a first annotation submitted for said Playable Media File: creating a table of contents by said network server for said Playable Media File; and encoding by said network server said data profile in said table of contents; wherein said Playable Media File is selected from the group consisting of an audio file, a video file, an audiovisual file, slide show, AVI file, MP3 file, MP4 file, WMA file, WAV file, Flash, and MPEG file.
 13. The article of manufacture 12, said computer readable program code further comprises a series of computer readable program steps to effect initiating a discussion thread within said Playable Media File at said location.
 14. The article of manufacture 12, wherein: the computer program readable step of receiving further comprises a computer program readable step of receiving a Playable Media file by a first member of a social network; the computer program readable step of creating further comprises a computer program readable step of creating an annotation by said first member of said social network; and the computer program readable step of providing steps are instructed by said first member of said social network to be effected by the processor.
 15. The article of manufacture 14, wherein the computer program readable step of initiating further comprises a computer program readable step of initiating by said first member a discussion thread within said Playable Media File at said location.
 16. The article of manufacture 12, said computer readable program code further comprises a series of computer readable program steps to effect storing said annotation as a file separate from said Playable Media File.
 17. The article of manufacture 16, said computer readable program code further comprising a series of computer readable program steps to execute said Playable Media File by a second member of said social network.
 18. The article of manufacture 17, wherein said first member differs from said second member.
 19. The article of manufacture 17, wherein said first member and said second member are the same.
 20. The article of manufacture 17, when said Playable Media File reaches said location, said computer readable program code further comprising a series of computer readable program steps of making said annotation visible.
 21. The article of manufacture 20, said computer readable program code further comprising a series of computer readable program steps of: displaying said executing Playable Media File in a first window; and displaying said annotation in a second window.
 22. The article of manufacture 20, said computer readable program code further comprising a series of computer readable program steps of displaying both said executing Playable Media File and said annotation in the same window.
 23. A non-transitory computer usable medium encoded with a computer program product to create and save an annotation associated with a Playable Media File and usable with programmable computer processor disposed within a controller, comprising: computer readable program code which causes said programmable computer processor to receive a Playable Media File; computer readable program code which causes said programmable computer processor to create an annotation relating to said Playable Media File; computer readable program code which causes said programmable computer processor to provide said annotation to a network server; computer readable program code which causes said programmable computer processor to provide a data profile to said network server, wherein said data profile comprises a location in said Playable Media File where said annotation should be made visible; computer readable program code which causes said programmable computer processor to determine by said network server if said annotation is a first annotation submitted for said Playable media File; if said annotation is not a first annotation submitted for said Playable Media File, computer readable program code which causes said programmable computer processor to encode said data profile in a previously-created table of contents for said Playable Media File; if said annotation is a first annotation submitted for said Playable Media File: computer readable program code which causes said programmable computer processor to create a table of contents by said network server for said Playable Media File; and computer readable program code which causes said programmable computer processor to encode by said network server said data profile in said table of contents; wherein said Playable Media File is selected from the group consisting of an audio file, a video file, an audiovisual file, slide show, AVI file, MP3 file, MP4 file, WMA file, WAV file, Flash, and MPEG file.
 24. The computer program product of claim 23, further comprising computer readable program code which causes said programmable computer processor to initiate a discussion thread within said Playable Media File at said location.
 25. The computer program product of claim 23, wherein: said receiving further comprises computer readable program code which causes said programmable computer processor to receive a Playable Media file by a first member of a social network; and said creating further comprises computer readable program code which causes said programmable computer processor to create an annotation by said first member of said social network.
 26. The computer program product of claim 25, wherein said initiating further comprises computer readable program code which causes said programmable computer processor to initiate by said first member a discussion thread within said Playable Media File at said location.
 27. The computer program product of claim 23, further comprising computer readable program code which causes said programmable computer processor to store said annotation as a file separate from said Playable Media File.
 28. The computer program product of claim 27, further comprising computer readable program code which causes said programmable computer processor to execute said Playable Media File by a second member of said social network.
 29. The computer program product of claim 28, wherein said first member differs from said second member.
 30. The computer program product of claim 28, wherein said first member and said second member are the same.
 31. The computer program product of claim 28, further comprising computer readable program code which causes said programmable computer processor to make said annotation visible when said Playable Media File reaches said location.
 32. The computer program product of claim 31, further comprising: computer readable program code which causes said programmable computer processor to display said executing Playable Media File in a first window; and computer readable program code which causes said programmable computer processor to display said annotation in a second window.
 33. The computer program product of claim 31, further comprising computer readable program code which causes said programmable computer processor to display both said executing Playable Media File and said annotation in the same window. 